Bump the npm-minor-patch group across 1 directory with 2 updates - #115

Sourced from @​playwright/test's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

• There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
• Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
• Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
• Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

• New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

  test('restart the server', { lock: '-exclusive-' }, async () => {
    // No other test runs while this one is running.
  });

• test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

  test('upload a file', async ({ page }) => {
    test.skip('Not implemented yet');
  });

... (truncated)

• a1f35e1 chore: mark v1.65.0 (#43925)
• a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
• 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65
• daf93bb cherry-pick(#43912): feat(chromium): roll to r1254
• 6545e89 cherry-pick(#43902): chore(deps): bump runtime deps
• 0347448 fix(test runner): track shared ESM dependencies for only-changed (#43837)
• 86e6924 fix(clock): cancel real-time timer when replay ends paused (#43873)
• d745ae0 fix(route): wait for all active handlers before disabling interception (#43889)
• 6e3f5ff docs: release notes for v1.65 (#43874)
• aa33d27 fix(chromium): honor Linux config directories for channel connections (#43884)
• Additional commits viewable in compare view

Sourced from posthog-node's releases.

posthog-node@5.63.1

5.63.1

Patch Changes

• #5545 28fe8c0 Thanks @​onmax! - Parse Node stack frames for functions named async without a leading parenthesis in the filename. (2026-11-06)
• Updated dependencies [28fe8c0]:
  • @​posthog/core@​1.64.1

posthog-node@5.63.0

5.63.0

Minor Changes

• #5580 aa66d4c Thanks @​haacked! - metrics.histogram() accepts a bounds option that sets the histogram's bucket boundaries, and beforeSend sees and can change them. The first sample of a histogram (name and unit) fixes its bounds until the client resets. A later sample with different bounds is recorded in the fixed buckets and logs a warning, and a sample with invalid bounds is dropped. The experimental posthog.flags.request.duration histogram now uses the bounds [50, 75, 100, 150, 200, 300, 400, 500, 750, 1000, 1500, 2000, 3000, 5000, 10000] ms, so its p50 and p95 resolve between 50ms and 5s. This changes the metric's buckets, which its experimental status allows. (2026-11-05)

Patch Changes

• Updated dependencies [aa66d4c]:
  • @​posthog/core@​1.64.0

posthog-node@5.62.0

5.62.0

Minor Changes

• #5509 71c2464 Thanks @​Silthus! - posthog.emails.send() can now send email content your code rendered, such as HTML from React Email. Give the email a templateKey and a subject, and pass html, text or both.

  const posthog = new PostHog("phc_...", { secretKey: "phs_..." });
  const { data, error } = await posthog.emails.send({
  to: "user@example.com",
  distinctId: "user_123",
  templateKey: "password-reset",
  subject: "Reset your password",
  html: renderedHtml,
  });
  if (error) throw error;
  // 'delivered', 'bounced', ...
  const { data: status } = await posthog.emails.get(data.id);

  You need a project secret API key, the kind that starts with phs_. Create one under Project secret API keys in your project settings. Set its Transactional email scope to Write to send emails, or to Read for a key that only reads statuses. Pass it to the client as secretKey. Set appHost to your PostHog app URL when you self-host PostHog or send through a reverse proxy.

  PostHog records each email's delivery, opens and clicks on the person with that distinctId. It groups every email with the same templateKey, so you see their metrics and logs in one place. The SDK retries a request that hits a network error, a rate limit or an outage twice by default. Every send carries an idempotency key, so a retry never sends the email twice. Pass your own idempotencyKey, such as welcome:user_123, and your job runner's retries are safe too.

... (truncated)

Sourced from posthog-node's changelog.

5.63.1

Patch Changes

• #5545 28fe8c0 Thanks @​onmax! - Parse Node stack frames for functions named async without a leading parenthesis in the filename. (2026-11-06)
• Updated dependencies [28fe8c0]:
  • @​posthog/core@​1.64.1

5.63.0

Minor Changes

• #5580 aa66d4c Thanks @​haacked! - metrics.histogram() accepts a bounds option that sets the histogram's bucket boundaries, and beforeSend sees and can change them. The first sample of a histogram (name and unit) fixes its bounds until the client resets. A later sample with different bounds is recorded in the fixed buckets and logs a warning, and a sample with invalid bounds is dropped. The experimental posthog.flags.request.duration histogram now uses the bounds [50, 75, 100, 150, 200, 300, 400, 500, 750, 1000, 1500, 2000, 3000, 5000, 10000] ms, so its p50 and p95 resolve between 50ms and 5s. This changes the metric's buckets, which its experimental status allows. (2026-11-05)

Patch Changes

• Updated dependencies [aa66d4c]:
  • @​posthog/core@​1.64.0

5.62.0

Minor Changes

• #5509 71c2464 Thanks @​Silthus! - posthog.emails.send() can now send email content your code rendered, such as HTML from React Email. Give the email a templateKey and a subject, and pass html, text or both.

  const posthog = new PostHog("phc_...", { secretKey: "phs_..." });
  const { data, error } = await posthog.emails.send({
  to: "user@example.com",
  distinctId: "user_123",
  templateKey: "password-reset",
  subject: "Reset your password",
  html: renderedHtml,
  });
  if (error) throw error;
  // 'delivered', 'bounced', ...
  const { data: status } = await posthog.emails.get(data.id);

  You need a project secret API key, the kind that starts with phs_. Create one under Project secret API keys in your project settings. Set its Transactional email scope to Write to send emails, or to Read for a key that only reads statuses. Pass it to the client as secretKey. Set appHost to your PostHog app URL when you self-host PostHog or send through a reverse proxy.

  PostHog records each email's delivery, opens and clicks on the person with that distinctId. It groups every email with the same templateKey, so you see their metrics and logs in one place. The SDK retries a request that hits a network error, a rate limit or an outage twice by default. Every send carries an idempotency key, so a retry never sends the email twice. Pass your own idempotencyKey, such as welcome:user_123, and your job runner's retries are safe too.

  A send with your own content also takes from, replyTo and captureEngagement: false. Set migratedFrom on the client to tell PostHog which email provider you moved from. A failed call returns an EmailError with PostHog's code and the HTTP statusCode.

  Docs: Send transactional emails with Node.js and the transactional email overview. (2026-11-05)

... (truncated)

• d2d8a26 chore: update versions and lockfile [version bump]
• 9644778 chore: update versions and lockfile [version bump]
• aa66d4c feat(metrics): give posthog.flags.request.duration finer buckets (#5580)
• 5663aff chore: update versions and lockfile [version bump]
• 71c2464 feat(node): send email content from code with emails.send (#5509)
• 25e06dc chore: update versions and lockfile [version bump]
• 88744a9 fix(node): skip local evaluation warnings for client-only flags (#5532)
• 0d8f89d ci(node): integrate shared benchmark reports (#5454)
• 03ca515 ci(node): add paired SDK performance benchmarks (#5453)
• 48f16d8 chore: update versions and lockfile [version bump]
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions